Skip to content

Conversation

@eraykeskinmac
Copy link
Contributor

@eraykeskinmac eraykeskinmac commented Nov 6, 2025

Proposed Content
I would like to propose adding 5 community tools to the Community Tools documentation, each as separate files following the utcp.md format.

Added Tools:

1. strands-hubspot

2. strands-teams

3. strands-telegram

4. strands-telegram-listener

5. strands-deepgram

Notes:

@zastrowm:

I added the nav items and split out Tool Protocols from Tools, as it looked weird having both. I also reordered the sections, as I expect tools to have the most entries and I didn't want to push down the rest of the integrations

Screenshots

image

Format Compliance
Each tool file follows the established pattern from utcp.md:

  • {{ community_contribution_banner }} included
  • Package description and purpose
  • Installation instructions
  • Usage examples with code snippets
  • Key features list
  • Configuration requirements
  • Resource links (PyPI, GitHub)

Community Value
These tools fill critical gaps in the Strands ecosystem:

  • Enterprise Communication: Teams integration for workplace workflows
  • CRM Integration: Safe HubSpot data access for sales intelligence
  • Global Messaging: Telegram ecosystem (800M+ users) with full send/receive
  • Speech Processing: AI-powered transcription and audio intelligence
  • Production Ready: All tools have comprehensive error handling and type safety

Add comprehensive documentation for community-contributed tools:

- strands-hubspot: READ-ONLY HubSpot CRM integration with safe data access
- strands-teams: Microsoft Teams notifications with Adaptive Cards
- strands-telegram: Complete Telegram Bot API with 60+ methods
- strands-telegram-listener: Real-time message processing with AI auto-replies
- strands-deepgram: Speech & audio processing with 30+ language support

Each tool follows the community contribution format with:
- Installation instructions
- Usage examples
- Key features
- Configuration requirements
- Resource links

All tools are production-ready with comprehensive error handling,
type safety, and detailed documentation for community adoption.
pgrayy
pgrayy previously approved these changes Nov 6, 2025
Copy link
Member

@zastrowm zastrowm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for these, looking pretty good and almost ready to merge.

I've left a couple of comments - could we update the entries to:

  • Have some yaml frontmatter (not blocking, but helpful)
  • Update the links in the entry paragraph (per comments)
  • (nit - align Requried/Optional comments)

@zastrowm
Copy link
Member

Are any of these replaced by https://github.com/eraykeskinmac/strands-tools-community? And/or did you want to call out https://github.com/eraykeskinmac/strands-tools-community in any of these pages?

- Added YAML frontmatter with project and service information
- Changed GitHub links to be primary (instead of PyPI first)
- Added service provider links (Deepgram, HubSpot, Teams, Telegram)
- Removed Strands SDK links (redundant in docs)
- Fixed environment variable alignment with proper comments
- Updated HubSpot link to working developer docs URL
- Added strands-tools-community meta-package references
- Fixed all issues raised by zastrowm in PR review
The strands-tools-community meta-package is deprecated as all tools
are now distributed as individual packages on PyPI. Removed the
alternative installation references from all tool documentation.
@eraykeskinmac
Copy link
Contributor Author

Are any of these replaced by https://github.com/eraykeskinmac/strands-tools-community? And/or did you want to call out https://github.com/eraykeskinmac/strands-tools-community in any of these pages?

Good question! No, the strands-tools-community repository is deprecated.

I originally created it as a meta-package to bundle all tools together, but decided to distribute each tool individually on PyPI instead. This approach provides:

  • Better dependency management - Users only install what they need
  • Independent versioning - Each tool can evolve at its own pace
  • Cleaner maintenance - Individual packages are easier to maintain
  • Standard Python packaging - Follows community best practices

I've removed all references to the deprecated meta-package from the documentation. Each tool now stands alone as its own PyPI package:

  • pip install strands-hubspot
  • pip install strands-deepgram
  • pip install strands-teams
  • etc.

Thanks for catching this! The docs are now cleaner without the outdated references.

eraykeskinmac and others added 4 commits December 4, 2025 05:08
Add strands-tools-examples repository link to all tool documentation.
This provides users with working examples, complete workflows, and
interactive demos for testing all community tools.

Repository includes:
- Individual tool examples with real-world workflows
- Interactive demo agent with REPL interface
- Complete setup guide with environment variables
- Telegram bot examples with AI-powered auto-replies
- End-to-end integration examples combining multiple tools

Example repository: https://github.com/eraykeskinmac/strands-tools-examples
@zastrowm zastrowm enabled auto-merge (squash) December 4, 2025 15:35
- Remove 'strands-agents[anthropic]' from installation as it's inconsistent
- Usage example uses default Agent() which works with Bedrock by default
- Users can still install anthropic separately if they prefer
- Keeps documentation consistent and simple
auto-merge was automatically disabled December 5, 2025 01:19

Head branch was pushed to by a user without write access

@pgrayy pgrayy merged commit 073a22c into strands-agents:main Dec 5, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants